Vcenter NamespaceManagement ProxyConfiguration

Vcenter NamespaceManagement ProxyConfiguration
Vcenter NamespaceManagement ProxyConfiguration

The Vcenter NamespaceManagement ProxyConfiguration schema defines proxy configuration to be used by the Supervisor.

This schema was added in vSphere API 7.0.3.00100.

JSON Example
{
    "proxy_settings_source": "string",
    "https_proxy_config": "string",
    "http_proxy_config": "string",
    "no_proxy_config": [
        "string"
    ],
    "tls_root_ca_bundle": "string"
}
string
proxy_settings_source
Required

The source of the proxy settings. If Vcenter NamespaceManagement ProxySettingsSource.VC_INHERITED or Vcenter NamespaceManagement ProxySettingsSource.NONE is specified, then the other configuration in Vcenter NamespaceManagement ProxyConfiguration will be ignored.

For more information see: Vcenter NamespaceManagement ProxySettingsSource.

This property was added in vSphere API 7.0.3.00100.

string
https_proxy_config
Optional

HTTPS proxy configuration. Examples:

This property was added in vSphere API 7.0.3.00100.

If missing or null no HTTPS proxy will be used.

string
http_proxy_config
Optional

HTTP proxy configuration. Examples:

This property was added in vSphere API 7.0.3.00100.

If missing or null no HTTP proxy will be used.

array of string
no_proxy_config
Optional

List of addresses that should be accessed directly. This will be used if Vcenter NamespaceManagement ProxySettingsSource.CLUSTER_CONFIGURED is used for the source, otherwise this will be ignored.

This property was added in vSphere API 7.0.3.00100.

If missing or null there won't be any excluded addresses.

string
tls_root_ca_bundle
Optional

Proxy TLS root CA bundle which will be used to verify the proxy's certificates. Every certificate in the bundle is expected to be in PEM format. This will be used if Vcenter NamespaceManagement ProxySettingsSource.CLUSTER_CONFIGURED is used for the source, otherwise this will be ignored.

This property was added in vSphere API 7.0.3.00100.

If missing or null only the vCenter certificates applied in VECS (VMware Endpoint Certificate Store) will be used.